bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Mon, 11 Oct 2021 18:36:19 +0000 (19:36 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Mon, 11 Oct 2021 18:36:19 +0000 (19:36 +0100)
commite80882373aef446dd21f2db0511246c1a088371b
treec0534ba3591dc4b6935dbc69138d7c027f8ab18a
parenteff685fa19486894646681a2820c017c881c6bfe
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h